On our infrastructure the queries mentioned in the comments in schema.prisma all cause full table scans because the only index is the primary key. As our verificationtoken table is pretty big, those queries have high latency (>100ms) and frequently cause significant CPU utilization spikes, disrupting all other database traffic.

Before creation of the indexes (not during a spike)

After creation of the indexes

Note how the SELECTs become a 1~2 orders of magnitude faster.

This is my first PR involving changes to the schema, so please let me know if the process is correct.

Relevant issues

Pre-Submission checklist

Please complete all items before asking a LiteLLM maintainer to review your PR

• I have Added testing in the tests/litellm/ directory, Adding at least 1 test is a hard requirement - see details
• My PR passes all unit tests on make test-unit
• My PR's scope is as isolated as possible, it only solves 1 specific problem

CI (LiteLLM team)

CI status guideline:

• 50-55 passing tests: main is stable with minor issues.
• 45-49 passing tests: acceptable but needs attention
• <= 40 passing tests: unstable; be careful with your merges and assess the risk.

• Branch creation CI run
  Link:

• CI run for the last commit
  Link:

• Merge / cherry-pick CI run
  Links:

Type

🐛 Bug Fix
🚄 Infrastructure

Changes